-
Notifications
You must be signed in to change notification settings - Fork 212
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
A3P commands without synthetic-chain #10396
Conversation
Deploying agoric-sdk with Cloudflare Pages
|
This comment was marked as resolved.
This comment was marked as resolved.
0d7f011
to
9a8474a
Compare
1fffdcb
to
3a18e22
Compare
3ea8635
to
b97d772
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Moving log
from options to io
makes more sense. Thanks.
|
||
In agoric-sdk CI and development, we want the proposals to use the versions of the packages in the agoric-sdk source tree. To accomplish this we use `yarn link`. In Yarn 4 (berry) it uses a `portal` protocol to link to another Yarn project on the filesystem. One kink is that in development the command would, | ||
``` | ||
yarn link --relative ../../.. --all |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So is this run only one time in your machine to create the resolutions in the n:upgrade-next/package.json
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Correct
LGTM, just asked a few small questions. I really appreciate the effort for this PR. Looking forward to seeing it support signing transactions as well. Willing to help for this if the need arises. |
6fdee12
to
f57d920
Compare
f57d920
to
2740748
Compare
closes: #10369
Description
Many of the imports from
@agoric/synthetic-chain
are not about synthetics per se. They should be possible with the code in agoric-sdk.This brings the new
@agoric/client-utils
into functional testing in a3p-integration. It makes the canonical source forsync-tool.js
that was duplicated in different proposal tests.This also demonstrates a style of smart-wallet offer execution without the
@agoric/synthetic-chain
package. SeeOpenVault
. It still goes throughexecSwingsetTransaction
spawningagd
but that could also be optimized with an RPC client lib for SwingSet that does signing (see #9200). That's out of scope for this effort to simply stop reliable in another repo for testing utilities.Review by commit is recommended
Security Considerations
n/a, tests
Scaling Considerations
n/a, tests
Documentation Considerations
When these patterns stabilize more we may want to write them down. For now I think let's keep it flexible.
Testing Considerations
per se
Upgrade Considerations
One impact to the upgrade process is that when moving a proposal from a3p-integration to agoric-3-proposals, the dependencies may have to be updated. Though it's likely they'll work on the
/usr/src/agoric-sdk
in the image